👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below.
🔍 Git commit SHA: db5be63
✅ Deployment Preview URL: https://projectpythia.github.io/_preview/566

Our nightly build failure included this as to metrics.md: unexpected figure content of type output found in legend node

But the PR was having trouble accessing the keys altogether?
ValueError: Unable to load PEM file. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details. MalformedFraming

Our metrics page says, "Last Updated: 2026-02-24 02:46:24.757143" with our last "successful" nightly build being 2026-02-23 at 7:45PM Mountain time. So it is the --strict call is messing with our metrics collection? Unlikely, probably due to nightly-build failing due to the broken links.

Not ideal, but PRs from forks will always fail to build metrics due to GitHub secrets/token handling. I tried 'myst build --execute --html --strict --exclude metrics.md' but exclude is not a valid MyST flag. Not sure turning off --strict is smart for PRs either, but it might be the only workaround available right now.

Any advice @agoose77 ? Can I somehow add "unexpected figure content of type output found in legend node" to the error-rules exclusions in the myst.yml file?

E: Seems the key for the above error is container-children-valid. It was harder to run myst --debug build because I had to track down our private key and key id that are hidden in GH secrets. But I got it.

I think ideally I'd like to change the pull request build test to something like `build_command: 'myst build --execute --html --strict --exclude metrics.md' so we still have strict testing for everything except an action that will always fail when run from a fork. If this is possible @agoose77 let us know!